Release 10.1A: OpenEdge Deployment:
Managing 4GL Applications

Platform

Starting with OpenEdge10.1A, 32-bit r-code only runs with the 32-bit product and 64-bit r-code only runs with the 64-bit product. This change provides performance benefits (such as very large memory) for the 64-bit product. However, it breaks the portability of r-code between 32-bit and 64-bit platforms.

You must recompile if you want to use the OpenEdge10.1A 64-bit product.

If portability between platforms is more important than 64-bit performance, you can use the 10.1A 32-bit product which can run 10.0x 32-bit and 64-bit generated r-code as well as 10.1A 32-bit generated r-code. The 10.1A 32-bit product can be installed and run on 64-bit hardware, but you will not see the performance benefits you get with the 10.1A 64-bit product.

Hardware related to 10.1A product

The 32-bit OpenEdge product can be installed and will run on either 32-bit or 64-bit hardware. The 64-bit OpenEdge product can be installed and will run on 64-bit hardware but not on 32-bit hardware.

10.1A product related to r-code

The 10.1A 32-bit product generates 32-bit r-code (4-byte aligned). This 32-bit r-code can run with the 10.1A 32-bit OpenEdge product. It can also run with the 10.0x 32-bit product and the 10.0x 64-bit product. It cannot run with the 10.1A 64-bit product.

The 10.1A 64-bit product generates 64-bit r-code (8-byte aligned). This r-code can only run with the 10.1A 64-bit product. (It cannot run with any 32-bit client, nor can it run with the 10.0x 64-bit product.)

Note: This platform issue only affects r-code. Both databases and network messages are compatible between 32-bit and 64-bit platforms.